|
2019-03-28 16:00 developer |
CPU Usage.png (69,234 bytes) |
|
|
We are checking on this issue. |
|
|
Hi Eric, We did changes in BT stack on V15.502.9 release. I don't see this issue happened. Could you update if this issue still exist on V15.502.9 release ? Thanks ! |
|
|
Hi Kerwin, BT's CPU usage is 0.7 ~ 1.6% when BT pairing or connection is getting failed. So this issue seems to be fixed in v15.502.9. |
|
|
included in v15.502.9 |
|
|
Hi Kerwin, It has been reproduced that BT's CPU usage is 100%. Please check it as soon as you can. For your reference, done rebooting STB under this issue has been observed, then STB displayed the previous BT pairing list. So we tried BT connection again and BT has been displayed as the connection, but BT is not working and its CPU usage is still 100%. BT status seems to be stuck. Here is the reproducible path. 1) Disconnect RCU BT via [*]+[Home] under RCU BT connection 1-1) Make sure that RCU is in BT connection status in the remote control & accessory menu 1-2) Verify if it's in the paired state by disconnecting BT 2) Retrying pairing BT via [*]+[#] 2-1) Must block IR and try it with only BT when performing to pair RCU 2-2) Verify if BT connection is displayed in the remote control & accessory menu 3) Verify RCU BT's behavior 3-1) Verify if RCU is working with only IR mode (RCU is not operating with BT mode) 3-2) Then BT's CPU usage reached upto 99~100% CPU Usage-2.png (172,658 bytes) |
|
|
Hi Eric, Jason shows me how to reproduce this issue, it seems 100% reproducible. I will check for the root cause, thanks for your information. |
|
|
Currently, the BT stack will try to connect to RCU even after RCU clear pairing information. During the connection, BT stack enter a infinite loop. We are looking for solution to fix it. |
|
|
Hi Kerwin, Just verified with your test version, the behavior is the same as Kaon STB's one that BT connection by only BT signal is failed, and BT connection is established normally when trying to pair BT again via [*]+[#]. So the test result is acceptable. |
|
|
Hi Eric, Thanks for your test result. We will include this fix in next release. |
|
|
Hi Kerwin, Just verified it with v15.502.12 version, and the test result is OK. Thanks for your effort! |
|
|
Hi Kerwin, Just verified it with v15.502.12 version, and the test result is OK. Thanks for your effort! |
- yk.jung ( (ALTech) Younkwang Jung ) developer
